| Field | Description |
|---|---|
|
Action |
This column provides the option to delete (X) any new fields you have previously added to existing entities. |
| Name |
This column contains the name of the data field. When adding new data fields, use intelligent naming conventions for the new fields by using a prefix that is defined by the entity’s name and the type of field you are adding. |
|
Label |
The label is the translation coming from the base translation file used by SmartSolve . It is not pulling in any additional form specific translation as it would not know which one to use. For field labels, the system first looks at changes in the following:
|
|
Validate Against |
Selecting an entity in this field pushes the entity to the Resolve Fields tab. See Managing Resolved Fields for additional information. For example, if the Department field must be validated against the existing Department list in SmartSolve, the designer must validate the field against the department table. |
|
Field Type |
The field type is a drop down field that will allow the designer to use default field types or field types that have been configured specifically to standardize the type and size of fields. |
|
Format Type |
This field is a drop down field that allows the designer to configure Date, Quantity, and Time formats for the appropriate field types. |
|
Status |
The status will display as Inworks if this is a field you just added that has not yet been published for use. Existing fields will display as Published. |
|
Enabled |
The system does not allow fields to be deleted once the entity has been published. This is done with the intent of avoiding losing user data, which the deletion of a field will cause, since the mapping between the entity field and the table column will be released when the field is deleted, leaving the column available for new mappings. In turn, a field can be disabled after the entity is published. Disabling a field is an indication that the field should no longer be used to store new data entered by the user and therefore should be removed in any form that uses it. The Forms Designer reflects the changes of a field being disabled by displaying it in a separate node in the data model tree. However, data entered prior to the disabling will still be available for reports or details forms. All default fields are enabled once the entity is published. If a field is no longer required to be used in the entity but has been used previously then it can be disabled by un-checking the Enabled option. |
|
User Key |
This represents the entity field that uniquely identifies the record. It is typically the field that is attached to the numbering scheme. |
|
|